Electronic Message Handling System and Method Between Sending and Recipient Devices with Separation of Display of Media Component and Header Information and Deletion of Electronic Message from Server

ABSTRACT

An electronic messaging system and method with reduced traceability by separation of display of media component of message content and header information. An electronic message having an identifier of a recipient and a message content including a media component is received at a server from a sending user device at which a display for associating the media component with the electronic message is provided without displaying the identifier of a recipient with the media component such that a single screen capture of the identifier of a recipient and the media component is prevented. The media component includes an image. The electronic message including an identifier of a sending user is transmitted to a recipient user device at which a display presenting the media component is provided without displaying the identifier of a sending user such that a single screen capture of both the identifier of a sending user and the media component is prevented. The electronic message is deleted from the server after being transmitted to the recipient user device.

RELATED APPLICATION DATA

This application is a continuation application of U.S. patentapplication Ser. No. 14/572,976, filed Dec. 17, 2014, and titled“Electronic Message Recipient Handling System and Method with MediaComponent and Header Information Separation”, now U.S. Pat. No.9,282,081, which is a continuation application of U.S. patentapplication Ser. No. 14/133,875, filed Dec. 19, 2013, and titled“Electronic Message Content and Header Restrictive Recipient HandlingSystem and Method,” now U.S. Pat. No. 8,935,351, which is a continuationapplication of U.S. patent application Ser. No. 13/651,909, filed Oct.15, 2012, and titled “Disassociated Content Electronic Message Systemand Method,” which is a continuation application of U.S. patentapplication Ser. No. 12/605,885, filed Oct. 26, 2009, and titled“Reduced Traceability Electronic Message System and Method For SendingHeader Information Before Message Content,” now U.S. Pat. No. 8,291,026,which is a continuation application of U.S. patent application Ser. No.11/401,148, filed Apr. 10, 2006, and titled “Reduced TraceabilityElectronic System and Method,” now U.S. Pat. No. 7,610,345, each ofwhich is incorporated by reference herein in its entirety. Thisapplication also claims the benefit of priority of U.S. ProvisionalPatent Application Ser. No. 60/703,367, filed Jul. 28, 2005, and titled“Method and System for Reducing Traceability of Electronic Messages,”which is incorporated by reference herein in its entirety.

This application is also related to the following commonly-ownedapplications: U.S. patent application Ser. No. 15/061,351, filed Mar. 4,2016, and titled “Electronic Message Handling System and Method BetweenSending and Recipient Devices with Separation of Display of MediaComponent and Header Information,” U.S. patent application Ser. No.14/572,920, filed Dec. 17, 2014, and titled “Electronic Message SendDevice Handling System and Method with Separation of Message Content andHeader Information,” U.S. patent application Ser. No. 14/572,932, filedDec. 17, 2014, and titled “Electronic Message Send Device HandlingSystem and Method with Separated Display and Transmission of MessageContent and Header Information,” U.S. patent application Ser. No.14/572,942, filed Dec. 17, 2014, and titled “Electronic Message SendDevice Handling System and Method with Media Component and HeaderInformation Separation,” U.S. patent application Ser. No. 14/572,952,filed Dec. 17, 2014, and titled “Electronic Message Recipient HandlingSystem and Method with Separation of Message Content and HeaderInformation,” U.S. patent application Ser. No. 14/572,966, filed Dec.17, 2014, and titled “Electronic Message Recipient Handling System andMethod with Separated Display of Message Content and HeaderInformation,” U.S. patent application Ser. No. 13/447,932, filed Apr.16, 2012, and titled “Reduced Traceability Electronic Message System andMethod,” and U.S. patent application Ser. No. 14/133,897, filed Dec. 19,2013, and titled “Electronic Message Content and Header Restrictive SendDevice Handling System and Method,” now U.S. Pat. No. 8,886,739, each ofwhich is incorporated by reference herein in its entirety.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the U.S. Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The present invention generally relates to the field of electronicmessaging. In particular, the present invention is directed to anelectronic message recipient handling system and method with mediacomponent and header information separation.

BACKGROUND

Typically, an electronic message between two people is not private. Itmay travel along a public network, such as the Internet, and besusceptible to interception by unintended third parties. Messages arealso logged and archived by the communication systems themselves. Theymay also be copied, cut, pasted, printed, forwarded, blind copied, orotherwise manipulated. This may give a message a “shelf-life” that isoften uncontrollable by the sender or even the recipient. Surreptitiouslogging (e.g., by keystroke and message recording software) may occur bythird parties that have gained unauthorized access to either thecomputer of the sender and/or the recipient. Electronic messages includethe message content itself coupled to identifying information regardingthe sender, the recipient, the location of the message, times and datesassociated with the message, etc. This allows a third party that islogging messages, intercepting messages, or simply gaining access to themessaging system's logs or inbox archives to associate the potentiallyimportant identifying information (typically referred to as headerinformation) with the message content. These are only some of the waysin which electronic messages can be misused. There is a demand for asystem and method for reducing the traceability of electronic messages.

SUMMARY OF THE DISCLOSURE

In one implementation, a computer-implemented method of handling anelectronic message is provided. The method includes receiving at arecipient user device a header information corresponding to a messagecontent that includes a media component; providing a first display viathe recipient user device, the first display including the headerinformation in a message list, the first display not displaying themedia component; receiving at the recipient user device the messagecontent including the media component, wherein the message contentincluding the media component and the header information are correlatedby a unique identifier; receiving a selection by the recipient user viathe first display, the selection directed to a portion of the messagelist corresponding to the header information; and in response to theselection, providing a second display via the recipient user device, thesecond display displaying the message content including the mediacomponent.

In another implementation, a machine readable hardware storage mediumcontaining machine executable instructions implementing a method ofhandling an electronic message is provided. The instructions include aset of instructions for receiving at a recipient user device a headerinformation corresponding to a message content that includes a mediacomponent; a set of instructions for providing a first display via therecipient user device, the first display including the headerinformation in a message list, the first display not displaying themedia component; a set of instructions for receiving at the recipientuser device the message content including the media component, whereinthe message content including the media component and the headerinformation are correlated by a unique identifier; a set of instructionsfor receiving a selection by the recipient user via the first display,the selection directed to a portion of the message list corresponding tothe header information; and a set of instructions for providing, inresponse to the selection, a second display via the recipient userdevice, the second display displaying the message content including themedia component.

In yet another implementation, a system for handling an electronicmessage is provided. The system includes a means for receiving at arecipient user device a header information corresponding to a messagecontent that includes a media component; a means for providing a firstdisplay via the recipient user device, the first display including theheader information in a message list, the first display not displayingthe media component; a means for receiving at the recipient user devicethe message content including the media component, wherein the messagecontent including the media component and the header information arecorrelated by a unique identifier; a means for receiving a selection bythe recipient user via the first display, the selection directed to aportion of the message list corresponding to the header information; anda means for providing, in response to the selection, a second displayvia the recipient user device, the second display displaying the messagecontent including the media component.

BRIEF DESCRIPTION OF THE DRAWINGS

For the purpose of illustrating the invention, the drawings show aspectsof one or more embodiments of the invention. However, it should beunderstood that the present invention is not limited to the precisearrangements and instrumentalities shown in the drawings, wherein:

FIG. 1 illustrates one example of a schematic diagram of an exemplarysystem for electronic messaging depicting an initial electronic messagebeing communicating from one user to another;

FIG. 2 illustrates one example of a computer environment that may beutilized to implement various aspects of the present disclosure;

FIG. 3 illustrates another example of a schematic diagram of anotherexemplary system and method of the present disclosure;

FIG. 4 illustrates another example of a schematic diagram of anotherexemplary system and method of the present disclosure;

FIG. 5 illustrates one example of a flow chart depicting one exemplarymethod according to the present disclosure;

FIG. 6 illustrates another example of a flow chart depicting anotherexemplary method according to the present disclosure;

FIG. 7 depicts an exemplary login display image;

FIG. 8 depicts an exemplary display image including a recipient addressinput portion;

FIG. 9 depicts an exemplary display image including an electronicmessage content input portion;

FIG. 10 depicts an exemplary display image including an electronicmessage listing portion; and

FIG. 11 depicts an exemplary display image including a reply messageinput portion.

DETAILED DESCRIPTION

The present disclosure provides a system and method reducingtraceability of an electronic message. In one embodiment, headerinformation and message content of an electronic message are displayedby a system and method of the present disclosure so that headerinformation and message content are not displayed at the same time. Aswill be clear to one skilled in the art from the disclosure below,separation of header information from message content reduces thetraceability of the electronic message. To further reduce traceabilityof an electronic message, header information may be automaticallydeleted at a first predetermined time and message content may beautomatically deleted at a second predetermined time (e.g., aftermessage content is viewed). In one example, the first and secondpredetermined times may occur sequentially (e.g., deleting headerinformation upon displaying message content and deleting message contentupon closing a display of message content), simultaneously (e.g.,deleting message content and associated header information upon closinga display of message content), or out of order such that the secondpredetermined time occurs before the first predetermined time (e.g.,displaying message content first, deleting message content, displayingheader information, then deleting header information). These and otheraspects of the present disclosure will be described in greater detailbelow with respect to various exemplary embodiments illustrated in FIGS.1 to 11.

FIG. 1 illustrates one embodiment of a system 100 for electronicmessaging depicting an electronic message 105 being sent from one userto another. System 100 may include any number of computers, such as thetwo user computers 110 and 115, coupled to a network 120. Network 120facilitates communication between computer 110 and computer 115. In oneexample, system 100 may be a closed system that may utilize open networkstructures (e.g., the Internet) for communication with users, but thatdoes not utilize open or third-party messaging systems (e.g., industrystandard email) that may increase the chance of message logging andimpact the recordless nature of an electronic message of the presentdisclosure. System 100 allows users of computers 110 and 115 tocommunicate with each other via one or more electronic messages, such aselectronic message 105 over network 120. As will be described in furtherdetail hereinafter, several aspects of system 100 reduce traceability ofelectronic messages, such as electronic message 105. In one example,electronic message 105 is automatically deleted from system 100 after itis viewed by the recipient to ensure that electronic message 105 cannotbe forensically recreated and to ensure there is no record of electronicmessage 105 ever existing on system 100 thereafter.

Although computers 110 and 115 are illustrated as workstation computers,any well known computer may be utilized in creating and/or viewingelectronic messages. Example computers include, but are not limited to,a personal computer, a workstation computer, a server computer, a laptopcomputer, a handheld device, a mobile telephone, a personal digitalassistant (PDA), another computing device capable of communicating anelectronic message via network 120, and any combinations thereof. System100 may include one or more server computers. In one example, system 100may reside substantially on a single server computer. In anotherexample, system 100 may be distributed across two or more servercomputers. In yet another example, system 100 may be distributed acrossa plurality of user computers without a server computer, such as in apeer-to-peer environment. In one such example, components of a messagingsystem according to the present disclosure and/or their functionality(e.g., storage of header information and message content, displaygeneration, reply generation, etc.) may occur at a recipient's usercomputer In still another example, system 100 may be distributed acrossone or more server computers and one or more user computers. One or morerelay servers or other systems may be utilized between server computersand/or user computers.

FIG. 2 illustrates one example of a computing environment in theexemplary form of a computer 200 within which a set of instructions, forcausing the computer to perform any one of the methodologies of thepresent disclosure, may be executed. Computer 200 may include aprocessing unit 205, a system memory 210, and a system bus 215 thatcouples various components including system memory 210 to processingunit 205. System bus 215 may be any of several types of bus structuresincluding, but not limited to, a memory bus, a memory controller, aperipheral bus, a local bus, and any combinations thereof, using any ofa variety of bus architectures. System memory 210 may include a readonly memory (ROM) 220 and a random access memory (RAM) 225.

A basic input/output system 230 (BIOS), including basic routines thathelp to transfer information between elements within computer 200, suchas during start-up, may be stored in ROM 220. Computer 200 may alsoinclude a storage/memory device 235 for reading and/or writinginformation. Example storage devices include, but are not limited to, ahard disk drive for reading from and/or writing to a hard disk, amagnetic disk drive for reading from and/or writing to a removablemagnetic disk, an optical disk drive for reading from and/or writing toan optical media (e.g., a compact disc), and any combinations thereof.Storage/memory device 235 may be connected to bus 215 by an interface.In one example, storage/memory device 235 and associatedcomputer-readable media provide nonvolatile storage of computer readableinstructions, data structures, program modules, and/or other data forcomputer 200. It will be appreciated by those skilled in the art thatother types of computer-readable media that can store data that isaccessible by a computer in a volatile and/or non-volatile manner mayalso be used in an example operating environment. Examples of othertypes of computer-readable media include, but are not limited to, amagnetic cassette, a flash memory media (e.g., a card and athumb-drive), a digital video disk, a Bernoulli cartridge, a randomaccess memory (RAM), a read only memory (ROM), and any combinationsthereof. A computer-readable medium, as used herein, is intended toinclude a single medium as well as a collection of physically separatemedia, such as, for example, a collection of compact disks or one ormore hard disk drives in combination with a computer memory.

A number of program modules can be stored on storage/memory device 235,including, but not limited to, an operating system, one or moreapplication programs, other program modules, program data, computerimplemented instructions for carrying out the system and methodologiesof the present disclosure, and any combinations thereof. A user mayenter commands and information into computer 200 through one or moreinput devices, such as a keyboard 240 and/or a pointing device 245.Other examples of an input device include, but are not limited to amicrophone, a joystick, a game pad, a satellite dish, a scanner, and anycombinations thereof. These and other input devices may be connected toprocessing unit 205 through an interface 250 that is coupled to bus 215.Example interfaces for connecting an input device include, but are notlimited to, a serial interface, a parallel interface, a game port, auniversal serial bus (USB), an IEEE 1394 (Firewire) interface, a directinterface to system bus 215, and any combinations thereof.

A display device 255 may be connected to system bus 215 via aninterface, such as a display generator/video adaptor 260. Exampledisplay devices include, but are not limited to, a cathode-ray tube(CRT) monitor, a plasma display, an LCD display, and any combinationsthereof. In addition to a display device, a computer may include one ormore other peripheral output devices, such as a speaker and a printer. Apen digitizer and an accompanying pen/stylus may be included in order todigitally capture freehand input. A pen digitizer may be separatelyconfigured or coextensive with a display area 265 of display device 255.Accordingly, a pen digitizer may be integrated with display device 255,or may exist as a separate device overlaying or otherwise appended todisplay device 255.

Computer 200 may include a network connection 270 for connecting to oneor more of a variety of networks, such as network 120 of FIG. 1, andremote computer devices thereon. Example network connections mayinclude, but are not limited to, a network interface card, a modem, andany combinations thereof. Example networks include, but are not limitedto, a wide area network (e.g., the Internet, an enterprise network), alocal area network (e.g., a network associated with an office, abuilding, a campus or other relatively small geographic space), atelephone network, a direct connection between two computing devices,and any combinations thereof. A network, such as network 120 may employa wired and/or a wireless mode of communication. In general, any networktopology may be used. It will be appreciated that FIG. 1 depicts onlyone instance of a system 100, and that other instances may be createdwhere one or more computers utilize system 100. One or morecommunication protocols may be utilized with system 100 and/or withnetwork 120. Example protocols include, but are not limited to, TCP/IP,Ethernet, FTP, HTTP, HTTPS, and any combinations thereof. In oneexample, a user of a computer, such as computers 110, 115 may accesssystem 100 (e.g., on one or more server computers) utilizing a secureprotocol as is well-known. A user computer, such as computers 110, 115may utilize one or more software applications and/or one or more systembased applications in communicating with system 100. Example softwareapplications include, but are not limited to, a web browser (e.g.,INTERNET EXPLORER, MOZILLA, and NETSCAPE), Java (e.g., J2ME), BREW, adirect access client (e.g., CITRIX), and any combinations thereof.Example system applications include, but are not limited to, MICROSOFTWINDOWS, UNIX, LINUX, APPLE operating system, X-WINDOWS, COCOA,POCKETPC, and PALM.

Referring to FIG. 1 an exemplary electronic message 105 is communicatedby a sending user utilizing computer 110 to system 100 for furthercommunication to a recipient user. Exemplary system 100 includes anelectronic message receiver 125 for receiving one or more electronicmessages, such as electronic message 105. Electronic message receiver125 is in communication with an electronic message storage module 130.An electronic message storage module, such as electronic message storagemodule 130, stores electronic messages received by electronic messagereceiver 125 utilizing one or more particular data storagemethodologies. Many data storage methodologies will be recognized bythose skilled in the art and those chosen for use with an electronicmessage storage module according to the present disclosure may be basedon the particular implementation of the messaging system and method.Example data storage methodologies may include, but are not limited to,one or more tables, a database, a file system, and any combinationsthereof. In one example, as will be described in greater detail below,electronic message storage module 130 stores header (“container”)information and message content separate from each other to minimizecorrelation by a third party between identifying information regardingthe electronic message (e.g., identification of sender, recipient,date/time of message, location of message) in the header information andthe content of the message. In an alternate example, message content andheader information may be stored together and separated during display.In one embodiment of the present disclosure, header information andmessage content are never stored or displayed together. In such a case,a correlation (e.g., a non-identifying message ID described in detailbelow) may be utilized to associate the two components.

Electronic message 105 as communicated to system 100 in the example ofFIG. 1 includes a recipient address 135 and a message content 140. Arecipient address, such as recipient address 135 may be an indicatorthat identifies a particular desired recipient of an electronic message,such as electronic message 105. In one example, a recipient address maybe a unique identifier (e.g., a screen name, a login name, a messagingname, etc.) established specifically for use with system 100 at userregistration with the system. In another example, a recipient addressmay be a pre-established electronic mail (email) address, text messagingaddress, instant messaging address, Short Messaging Service (SMS)address, a telephone number (e.g., a home, work, mobile telephonenumber), BLACKBERRY personal identification number (PIN), or the like,that is associated with the recipient and provided by a third-partyprovider. Example third-party providers include, but are not limited to,a web-based commercial fee and fee-free provider (e.g., YAHOO, HOTMAIL,AMERICA ONLINE, etc.), an Internet service provider (e.g., AMERICAONLINE, MSN, cable operator, telephone company, etc.), a telephoneprovider (e.g., VERIZON, CINGULAR, etc.), BLACKBERRY provider, anemployer, an educational institution, and other email providers. Thethird-party address may be chosen by a user as their unique identifierat registration. In an alternative embodiment, a sending user may know athird-party address of an intended recipient and use it as a recipientaddress when generating electronic message 105. In such an embodiment,it is possible that the intended recipient is not a registered user ofsystem 100. In one example, system 100 may optionally include anexternal system communication generator 145 configured to send anotification message to the third-party system associated with therecipient address used with electronic message 105. External systemcommunication generator 145 is in communication with the appropriatenetwork for communication with the corresponding third-party address fordelivering the notification message. In one example shown in FIG. 1,external system communication generator 145 is shown connected to theInternet. In one example, a notification message may include anindication that someone has sent the desired recipient an electronicmessage on system 100 and that the intended recipient may register touse system 100. The notification message may include directions (e.g., ahyperlink) to a publicly available portion of system 100 forregistration.

An electronic message may be any electronic file, data, and/or otherinformation transmitted between one or more user computers. Anelectronic message may include (e.g., as part of a message content) anyof a wide variety of information including, but not limited to, text, animage, video (e.g., single play video utilizing an application, such asMACROMEDIA FLASH), binary, tabular data (e.g., a spreadsheet), rich textincluding variable font color, tables, etc.), audio (e.g., single playaudio utilizing an application, such as MACROMEDIA FLASH), other typesof data, and any combinations thereof. In one example, a message contentof an electronic message may include embedded information. In anotherexample, a message content of an electronic message may include anattached and/or linked file. In such an example with an attached and/orlinked file, the attached and/or linked file may be automaticallydeleted from the messaging system after being viewed by a recipient.Typically, a message content, such as message content 140 does notinclude information that in itself identifies the message sender,recipient, location of the electronic message, or time/date associatedwith the electronic message.

System 100 may optionally include a message ID generator 150. Asdescribed in further detail below, message ID generator 150 may generatea message ID for each electronic message received by system 100. Themessage ID is associated with the corresponding message. A message ID isused to associate a container (i.e., header) information with acorresponding separately-stored message content. In one example, amessage ID may be created using a unique 128 bit, randomly generatednumber. System 100 may include a correlation between header informationand message content in a variety of ways including, but not limited to,a database, a lookup table, an entry in a file system, and anycombinations thereof. Utilizing a message ID associated with anelectronic message, such as electronic message 105, system 100 mayhandle (e.g., store, deliver, display, etc.) a header information and amessage content of a particular electronic message separately with theability to correlate the two at a later time. Thus, a message contentmay be handled without any of the identifying header information. Amessage ID may contain unique and/or non-unique information. Forexample, a message ID may include a sequence number (e.g., 1, 2, 3, 4,etc.) identifying a number of a message amongst a group of messages. Asequence number may be re-used. For example, when an electronic messagewith a sequence number of “1” is viewed and subsequently deleted,sequence numbers for remaining electronic messages may be adjusted sothat the electronic message having sequence number “2” is renumbered tonumber “1” and so forth. In another example, a message ID may include asequence number and a unique user identifier (e.g., a user ID, a loginID, etc.).

System 100 may optionally include a reply ID generator 155. As describedfurther below, reply ID generator 155 generates a reply ID for eachelectronic message received by system 100. The reply ID associates anelectronic message, such as electronic message 105, with the sender ofthe electronic message. In one example, a reply ID may include noinformation that in itself would identify a sender of an electronicmessage to a third party that does not have access to the correlationmaintained by the messaging system. System 100 may include a correlationbetween a reply ID and a corresponding message sender in a variety ofways, including, but not limited to, a database, a lookup table, anentry in a file system, and any combinations thereof. In one aspect, areply ID associated with an electronic message allows the headerinformation and/or the message content of the electronic message toinclude no information about the sender of the message that itselfprovides a traceable identity of the sender. As described in more detailbelow, a recipient may still send a reply electronic message to theoriginal sender. Additionally, a third-party that may intercept, log, orotherwise come in possession of the header information and/or themessage content will not be able to trace the electronic message to thesender without also gaining access to the correlation maintained bysystem 100. A reply ID may include a variety of different identifiersthat allow a messaging system, such as system 100, to direct a replyelectronic message back to a sender of the original electronic message.In one example, a reply ID may be created using a randomly generatednumber (e.g., a 128 bit, randomly generated number).

System 100 includes a display generator 160 in communication withelectronic message storage module 130. Display generator 160 isconfigured to provide information representing a display image fordisplay on a user computer, such as user computers 110, 115. Exampledisplay images include, but are not limited to, a user login display, adisplay listing information representing available electronic messagesfor viewing, a display for entering an electronic message, a display ofa message content of an electronic message, a display for entering areply electronic message, and any combinations thereof. In one example,display generator 160 may be configured to utilize a message ID ingenerating a first information 165 representing a first display imageincluding at least some of the header information for electronic message105. Display generator 160 may also be configured to generate a secondinformation 170 representing a second display image including messagecontent 140 of electronic message 105. FIG. 1 illustrates first andsecond information 165, 170 communicated with computer 115 for displayto a recipient user. In this example, display generator 160 generatesfirst and second information 165, 170 in a manner that does not allowthe first and second display images to be displayed at the same time.Separate display of header information and message content for anelectronic message reduces traceability of the electronic message. Inone aspect, screenshot logging at a computer, such as computer 115, maynot capture both header information and message content simultaneously.Additionally, separation of header information and message contentphysically and/or temporally during communication to a user computerover an open network, such as the Internet, can thwart misuse of theelectronic message by reducing the ability of intercepting bothcomponents of the electronic message.

Display generator 160 may utilize any of a variety of well known displaygeneration methodologies and/or protocols for creating informationrepresenting a displayable image. Example methodologies/protocolsinclude, but are not limited to, hypertext markup language (HTML),extensible markup language (XML), direct graphic generation, and anycombinations thereof. In one example, system 100 resides on one or moreserver computers and display generator 160 includes and/or utilizes aweb server application to generate information representingweb-browser-displayable images that may be viewed by a user computerincluding a web browser. In another example, display generator 160 maybe configured to instruct a browser or other application of a usercomputer displaying a display image according to the present inventionto not cache any of the information related to the display image.

System 100 may further include a deletion module 175 in communicationwith electronic message storage module 130. Deletion module 175 isconfigured to delete header information and/or message content fromsystem 100 after a predetermined amount of time. In one example,deletion module 175 is configured to automatically delete headerinformation and corresponding message content immediately after themessage content is displayed. In another example, a deletion module(e.g., deletion module 175) is configured to automatically delete headerinformation upon display of a corresponding message content. In yetanother example, a deletion module (e.g., deletion module 175) isconfigured to automatically delete message content upon a display of themessage content being closed. In still another example, a deletionmodule is configured to automatically delete header information and/ormessage content, whether or not they have been viewed, after apredetermined time (e.g., twenty-four hours after being received). Instill yet another example, a deletion module is configured toautomatically delete header information and/or message content apredetermined time (e.g., twenty-four hours) after first beingdisplayed. In a further example, a predetermined amount of time mayinclude a predetermined number of viewings (other than a single viewing)of a particular electronic message (e.g., an electronic message isdeleted after 20 views). In still a further example, a deletion module(e.g., deletion module 175) is configured to automatically delete headerinformation upon display of a corresponding message content and toautomatically delete message content upon a display of the messagecontent being closed. Combinations of deletion protocols, such as theseexamples, are also contemplated.

In an alternate embodiment, system 100 may include a display-basedkeyboard generator 180. Display-based keyboard generator 180 isconfigured to generate a display-based keyboard that may be includedwith a display image generated by display generator 160. A display-basedkeyboard can be utilized by a user (e.g., through mouse click or touchscreen depression) to input information (e.g., username, password,recipient address, message content) without the use of the standardkeyboard associated with the user computer. In this way interception bykeyboard (keystroke) logging hardware and/or software resident on theuser computer, such as computers 110, 115, can be avoided. In oneexample, a display-based keyboard generator may utilize FLASH technologycommercially available from Macromedia Inc. In another example, adisplay-based keyboard generator may utilize Java technologycommercially available from Sun Microsystems. In one aspect aFLASH-based keyboard may randomly place spaces between characters in theon-screen keyboard to further prevent interception of the message.Although this is a relatively slow data entry method, a user can be moreassured that their information is not being logged and/or intercepted.

System 100 may also optionally include a reply message receiver 185.Reply message receiver 185 is configured to receive a reply message toone or more original electronic messages viewed by a recipient. In oneaspect, a sender of an original electronic message may be determinedfrom an identifying characteristic included, or associated, with theelectronic message. Example identifying characteristics include, but arenot limited to, a reply ID, an email address, a username, a displayname, login ID, and any combination thereof. In one example, a reply IDof the original electronic message may be utilized in generating a replymessage. In one example, a reply message as communicated by computer 115to system 100 need only include a message content 190. System 100 mayinclude a reply generator 195. Reply generator 195 may be configured toutilize the original reply ID to associate message content 190 and anycorresponding header information with the original electronic messagesending user. Message ID generator 150 may be configured to generate amessage ID for the reply electronic message (i.e., message content 190and corresponding header information). Reply ID generator 155 may beconfigured to generate a new reply ID for the reply message andelectronic message storage module 130 may store message content 190 andcorresponding header information separately for later display to theuser (original sender).

FIG. 1 illustrates only an exemplary embodiment of a messaging systemand networking environment according to the present disclosure. As willbe appreciated by those skilled in the art and as described herein,variations to system 100 and the network environment may be utilized inimplementing the various aspects and methodologies of the presentdisclosure. FIGS. 3 and 4 illustrate alternate computing environments.FIG. 3 illustrates one embodiment of a messaging system 300 according tothe present disclosure. System 300 includes a computing environmenthaving a single server computer 310. User computers 315 and 320communicate with server computer 310 via network 325. An electronicmessage 330 is communicated utilizing system 300. A reply electronicmessage 340 is also illustrated. FIG. 4 illustrates another embodimentof a messaging system 400 according to the present disclosure. System400 includes a computing environment having two server computers 405,410. User computers 415 and 420 communicate with server computers 405,410 via network 425. An electronic message 430 is communicated utilizingsystem 400. A reply electronic message 440 is also illustrated. Servercomputers 405, 410 together perform the functionality of the singleserver computer 310 of FIG. 3.

Referring to FIGS. 3 and 5, an exemplary operation of a messaging systemaccording to the present disclosure, such as system 300, can bedescribed. A user may log into system 300 at computer 315 (step 505 ofFIG. 5). For example, a user may access a web site or other networkedinterface associated with server 310. Server 310 may then provideinformation representing a display image (e.g., a web page) for displayon computer 315 that allows the user to log into the system. In oneaspect, a user of system 300 may have associated therewith a login IDand password for logging into system 300. FIG. 7 depicts an examplelogin display 700 that may be used. In one aspect, system 300 mayprovide an instruction to a browser or other application on computer315, or other computer viewing a display image according to the presentdisclosure, to not cache the information contained in the display image.Upon entry of a valid login ID and password, server 310 establishes acommunications link with computer 315 (e.g., a key infrastructure,secure sockets layer (SSL), secure HTTP (HTTPS) or other secure ornon-secure communications link). In one example, system 300 may utilizean email address as a login ID.

In one aspect, while a user is logged into system 300, a session may beestablished including the establishment of a session ID. A session and acorresponding memory may be utilized by system 300 to maintain certaininformation regarding the session and the user (e.g., user'sidentification information, a reply ID).

Upon proper login, the user may be presented with a session startingdisplay image. One of skill in the art will appreciate that a variety ofstarting display images (i.e., pages) may be available for display to auser upon initial login to system 300. In one example, a display imagefor inputting an electronic message may be displayed. FIG. 8 illustratesone example of a starting display image 800. Display image 800 includesa first portion 805 for entering a recipient address or other identifierfor one or more recipients of a message. Display image 800 alsoillustrates an “inbox” portion 810 for listing unread electronicmessages on the system for the logged in user. In this example, anoptional display name 815, “Mary Smith” for the logged in user isdisplayed. A display name may be the same or different from acorresponding login name and/or user address, and may or may not includeidentifying information regarding the user.

Upon entering a recipient address (step 510 of FIG. 5) and activating abutton 820 or other trigger, a message content display screen, such asmessage content display screen 900 of FIG. 9 may be displayed. Displayscreen 900 includes a first portion 910 for inputting (step 515 of FIG.5) a message content corresponding to the recipient address input atportion 805 of FIG. 8. In this example, the recipient address and themessage content are entered on separate display screens. In anotherexample, the recipient address and message content may be input on asingle display image screen. Separation of the entry of the recipientaddress and message content further reduces the traceability of anelectronic message by, in part, reducing the ability of logging atcomputer 315.

In an alternative embodiment, a display-based keyboard (as discussedabove) may be included in an electronic message input displays, such asdisplay images 700, 800, and 900. A user may use a mouse or otherpointing device (e.g., a touchscreen display) to select characters beingentered.

FIG. 9 illustrates an example message content 930 having been entered inportion 910. Upon completion of message content entry, a user may selectbutton 940, or other indicator, to communicate message content 930 toserver 310 (step 520 of FIG. 5). In one example, the recipient addressmay be communicated to server 310 separately from a correspondingmessage content at the time of entry. This may reduce the ability tointercept the entire electronic message during communication to server310. In another example, the recipient address may be retained atcomputer 315 until the entry of corresponding message content in asubsequent display image. In one example, upon communication of therecipient address and message content 930, computer 315 retains no traceof the either the recipient address or message content 930. For example,each may exist only in random access memory (RAM), and possibly invirtual memory (e.g., a page file) established in a disk drive, atcomputer 315 from the time the user types the information until theloading of the next display image at computer 315, after which theinformation is effectively deleted. Referring to FIG. 3, electronicmessage 330 is illustrated as including a recipient address and messagecontent that is communicated from computer 315 to server 310.

In an alternate embodiment, upon server 310 receiving electronic message330, instructions associated with system 300 (e.g., instruction storedat server 310) generates a reply ID and associates the reply ID withelectronic message 330 (step 525 of FIG. 5). Server 310 maintains acorrespondence between the reply ID and the sending user. In oneexample, a new reply ID is created for each electronic messageregardless of whether the sending user is the same as another electronicmessage. This enhances the reduced traceability of the electronicmessage.

In another alternate embodiment, at step 530, system 300 generates amessage ID for associating the separated message content and headerinformation of electronic message 330. Server 310 maintains acorrespondence between the message content and header information.

At step 535, header information associated with electronic message 330is identified for separation from message content 930. In one aspect,separation of information that identifies the sending user, recipientuser, location of the electronic message, timing of electronic messagefrom the message content may be implemented by associating suchinformation with a container or header information component of theelectronic message. In one example, utilization of a reply ID and amessage ID can further facilitate the removal of information that itselfidentifies a sending user or recipient. A display name for the sendinguser may be generated and associated with the header information. Thedisplay name for the user need not be unique, thus maintaining theanonymity of the user when electronic message 330 is ultimatelycommunicated to computer 320 or otherwise viewed by the recipient. Inone example, system 300 replaces all information associated withelectronic message 330 that could itself identify the sending user. Inone embodiment, a predetermined display name for the sending user thatdoes not provide unique identification of the sending user may begenerated and associated with corresponding header information. Inanother example, system 300 may utilize a display name that includesinformation that uniquely identifies the sending user (e.g., login name,email address, etc.).

In one example, header information for a particular electronic message,such as header information, may include, but is not limited to, a replyID, a message ID, a date/time associated with the electronic message(e.g., date/time of creation, date/time of delivery, etc.), a displayname representing a sender of the electronic message, and anycombinations thereof.

At step 540, an electronic message 330 is associated with a recipientrepresented by the recipient address. In one example, a location of therecipient is determined. As used herein, a location may include amessage mailbox, a message server associated with the recipient, acomputer associated with the recipient, an electronic address of therecipient, a display name for the recipient in system 300, or the like.For example, system 300 may identify a user by a variety of identities(e.g., display name, login ID, associated email address, text messagingaddress, instant messaging address, SMS address, mobile number,BLACKBERRY PIN, or the like) to determine a routing for electronicmessage 330. As discussed above, if the recipient is not a registereduser of system 300, a notification may be sent to a third-party systemof the existence of electronic message 330. For example, if therecipient is identified by a third-party email address, a notificationmay go to the email recipient over the third-party email network.Similarly, if the recipient is identified by a Blackberry PIN, anotification may go to the recipient over the Blackberry network.

At step 545, header information and message content are stored. In oneexample, header information and message content are stored separatelyfrom each other (e.g., in separate files, in separate databases, inseparate tables, etc.). A message ID may be used to maintain acorrespondence between the separated components of electronic message330. Storage may occur in a variety of ways including, but not limitedto, storage at a location of the recipient and storage at server 310. Inone example, the header information and message content of electronicmessage 330 are stored in a storage medium of server 310 in separatetables.

In another example, each user of system 310 is assigned a storagedirectory (e.g., on a server, on a user computer such as in apeer-to-peer arrangement, etc.). Upon association of a user with therecipient address, the message content and header information for anyelectronic messages to that user may be stored in that user's storagedirectory. The following XML file definition illustrates an example ofheader information for two electronic messages stored in a user storagedirectory.

<?xml version=“1.0” encoding=“UTF-8” ?> <streams> <streamsummaryid=“8C515D3B6A3A99C6C1A1F1DE019C7AB0”   from=“user one”datereceived=“1143660969”   replyid=“6C04279318E53F61A9D7984ADD4C3E1A /><streamsummary id=“98F78AD49BFC35B36357850C107460DF” from=“user four  [mike.smith@onlinemail.com]” datereceived=“1143665437”  replyid=“0648B99BE6F9E5AB21F3A163AD242173” /> </streams>

The above file definition includes a message ID (“streamsummary id”), adisplay name (“from”), date received, and reply ID for each message inthe recipients storage directory. Note that as an implementationvariation, the sending user of the second message has associatedtherewith a display name, “user four”, which includes a reference to anemail address, mike.smith@onlinemail.com. This email address may or maynot be associated with an actual email account of a third-party system,and may or may not provide actual identifying information related to thesending user. The following message content XML file is storedseparately in the storage directory from the above header information.

<?xml version=“1.0” encoding=“UTF-8” ?> <messageid=“8C515D3B6A3A99C6C1A1F1DE019C7AB0” ” subject=“”> <text>This is myfirst message to you.</text> </message>

The following second message content XML file is stored separately inthe storage directory from the header information.

<?xml version=“1.0” encoding=“UTF-8” ?> <messageid=“98F78AD49BFC35B36357850C107460DF” subject=“”> <text>This is a replymessage to your message from Monday.</text> </message>

Each of the message content XML files includes the corresponding messageID for correlation back to the corresponding header information. Eachmessage content XML file also includes the message content. One skilledin the art would recognize other storage methodologies for separatingheader information from message content that are consistent with thepresent disclosure.

Referring again generally to FIG. 5 at step 550 to describe theretrieval of an electronic message by a user, a recipient user logs intosystem 300 using computer 320. A display image similar to that in FIG. 7may be utilized as a login display. In one example, upon entry of avalid login ID and password, a communication link between computer 320and server 310 is established. At step 555 of FIG. 5, a display imagehaving header information is communicated (e.g., from server 310 tocomputer 320. System 300 provides a display image to computer 320representing at least some of the header information associated with anyelectronic messages associated with the recipient user. FIG. 10illustrates an example display image 1000 including a recipient addressinput portion 1005 and a message listing portion 1010. Message listingportion 1010 includes a list of header information 1015, 1020, 1025 ofthree electronic messages. Message listing portion 1010 includes adisplay name and a date/time received for each of header information1015, 1020, 1025. Each message container (or header information) 1015,1020, 1025 may also include an association to a message ID and anassociation to a reply ID (although, not displayed in display image1000). Message content for each electronic message is not displayed viadisplay image 1000.

FIG. 3 illustrates header information and a message content forelectronic message 330 being communicated to computer 320. In thisexample, header information 1015 represents electronic message 330.

In an alternate embodiment, the header information communicated tocomputer 320 may include a sequence number (ex: 1, 2, 3, etc.) assignedto each electronic message associated with a particular user and/or sentto a particular computer. In such an embodiment, each sequence numbermay be associated in system 300 with the corresponding message ID. Themessage ID may be removed from the corresponding header informationand/or message content. In this manner, system 300 may avoid sending amessage ID to a user computer and instead may send the sequence number,which may be reused when a message is deleted and is, therefore, lesstraceable from the user computer.

At step 560, a user may select one of the electronic messages indicatedby header information 1015, 1020, 1025 (e.g., by selecting acorresponding “read” indicator in message listing 1010). At the time ofselection, the message content for each electronic message may not havebeen communicated to computer 320. In one example, message content maybe communicated to computer 320 along with corresponding headerinformation (but, not displayed). In another example, message contentmay be retained at server 310 until a second request from a user is sentto server 310 to view a message content of a particular electronicmessage. In such an example, computer 320 requests a message content fora selected electronic message (e.g., electronic message 330 via headerinformation 1015) from server 310. In response to this action, server310 may associate a message ID from the selected header information andcommunicate the message content having the corresponding message ID tocomputer 320. Alternatively, where a sequence number is utilized foreach electronic message, server 310 associates the sequence number ofthe selected electronic message with a corresponding message content andcommunicates the message content to computer 320.

At step 565, a display image including the message content, but none ofthe header information, is provided at computer 320. FIG. 11 illustratesone example display image 1100 presenting message content, independentof header information, for electronic message 330 upon the selection ofheader information 1015 in display image 1000 of FIG. 10. Display image1100 includes a message content portion 1110 including the messagecontent of electronic message 330. Display image 1100 also includes areply message input portion 1120.

In one alternate embodiment, display image 1100 may employ FLASHtechnology to display the message content. For example, display image1100 may require the user to “park” the on-screen cursor in an area indisplay image 1100 to see the message content, which may be displayed asa Flash movie. Should the cursor be moved, the displayed message contentwill be hidden from view on the screen to allow the user to quicklyprevent the message content from being seen by onlookers. Also, thistechnology may also be utilized to prevent the message content frombeing printed using the web browser or application print because themessage content will be hidden as soon as the user moves the mouse inattempt to print. In another example, the use of Cascading Style Sheets(CSS) may allow the portion of the display image including the messagecontent to be not shown or hidden during printing.

Referring to FIG. 5, at step 570, the electronic message, such aselectronic message 330, is automatically permanently deleted from server310 at a predetermined time at step 565. In one example, headerinformation is deleted from server 310 upon its communication tocomputer 320, and then the corresponding message content is deleted fromserver 310 upon its communication to computer 320. In such an example,once message list 1010 is displayed to a user, the user must view themessage content during that session. To achieve the ability to view onemessage content and return to message list 1010, the header informationfor non-viewed electronic messages may be retained in memory at computer320. In another example, header information is retained at server 310until the corresponding message content is viewed, at which point boththe header information and the message content is deleted from server310. A reply ID for a particular electronic message may be retained inmemory of server 310 (e.g., in response to a request for viewing amessage content, server 310 may associate a current session ID with thereply ID) until the display image that displays the correspondingmessage content is closed by the user. This will allow a user to utilizereply message portion 1120 of display image 1100 to reply to the currentmessage content without having to have a unique address for the originalsender associated with the message content on computer 320. FIG. 3illustrates a server-based system. Deletion from an alternate system,such as a peer-to-peer system, may include deletion of an electronicmessage from storage at a user computer.

As discussed above, other examples of deletion times for deletion from asystem, such as system 300, include, but are not limited to, automaticdeletion of header information and corresponding message contentimmediately after the message content is displayed, automatic deletionof header information upon display of a corresponding message content,automatic deletion of message content upon a display of the messagecontent being closed, automatic deletion of header information and/ormessage content (whether or not they have been viewed) after apredetermined time (e.g., twenty-four hours after being received),automatic deletion of header information and/or message content apredetermined time (e.g., twenty-four hours) after first beingdisplayed, and any combinations thereof. In one example, system 300 isconfigured to require a given deletion scheme (e.g., automatic permanentdeletion of an electronic message upon displaying the electronic messageand/or one or more of its components) regardless of a desire of asending and/or recipient user.

One example of a deletion algorithm appropriate for deletion ofelectronic messages from system 300 include, but is not limited to, USDepartment of Defense (DoD) clearing and sanitizing standard DoD5220.22-M. In an alternative embodiment, server computer 310 may deletean electronic message, such as electronic message 330 and thecorresponding reply ID from its own memory if the recipient fails toretrieve the electronic message within a predetermined amount of time.

In one example, after viewing the message content, the user may select alink 1130 on display image 1100 to return to the message listing (e.g.,message listing 1010 of FIG. 10), or otherwise close the display image(step 575 of FIG. 5). In another example, after viewing the messagecontent, the user may choose to respond to electronic message (step 580of FIG. 5), as will be described in further detail hereinafter. If theuser fails to respond to the message content within a predeterminedamount of time (e.g., 1 hour) an associated reply ID may be deleted fromserver 310. If the user chooses to return to the listing of messages,the message content may be automatically deleted from the recipient'scomputer 320 after viewing (step 585 of FIG. 5). For example, themessage content will exist only in RAM, and possibly in virtual memoryestablished in the disk drive, in computer 320 from the time the userviews the message content until the loading of the next screen intocomputer 320, after which the message is effectively deleted.Furthermore, in one example, the listing of messages (e.g., messagelisting 1010 of FIG. 10), will no longer include the header informationfor a particular electronic message (e.g., header information 1015 ofelectronic message 330) that has been deleted from server 310, and thesession ID will no longer include reference to the reply ID. In otherwords, the user will not be able to view that message again or reply tothe message once it has been deleted.

In an alternative embodiment, electronic messages may be sent, stored,and/or retrieved using encryption technology. Various encryptiontechnologies are known to those skilled in the art. For example, acombination of public and private encryption keys may be utilized byusers and the system to further ensure security and reduce traceabilityof electronic messages until deletion.

Referring to FIGS. 3 and 6, operation of system 310 in optionallysending a reply message 340 from user computer 320 to user computer 315can be described. As shown for example in FIG. 11, the recipient user ofthe original electronic message (e.g., electronic message 330) maychoose to reply to the message utilizing reply message input portion1120. Reply message input portion 1120 allows a user to input a messagecontent for a reply message. In this example, there is no need to inputa recipient address as an original reply ID may be utilized by system300 in determining the routing of the reply electronic message. Afterthe user completes reply message input portion 1120, he or she mayselect the “send stream” button 1140. In response, computer 320communicates the reply message content to server computer 310 (step 605of FIG. 6). After the reply message content is communicated, computer320 retains no trace of the message's existence. For example, themessage will exist only in RAM, and possibly in virtual memoryestablished in the disk drive, in computer 320 from the time the usertypes the message until the loading of the next screen into computer320, after which the message is effectively deleted. In an alternativeembodiment, a display-based keyboard, as discussed above, may beutilized as part of display image 1100 for inputting reply messagecontent.

In one example, upon receipt of the reply message content, server 310determines the reply ID for the original message (e.g., from the currentsession ID), and uses the reply ID to associate the electronic messagewith the user that sent the original message 330 (step 610 of FIG. 6).This may be accomplished in a variety of ways including, but not limitedto, a lookup table, a database, or the like, which provides acorrelation between the reply ID and the sender of the initial message.At step 615, system 300 then deletes the initial reply ID (e.g., thereply ID for message 330) from server 310's memory. In an alternateembodiment, the identity of the sender of an original electronic messagemay be determined from another identifier associated with the electronicmessage (e.g., display name, login ID, associated email address, textmessaging address, instant messaging address, SMS address, mobilenumber, BLACKBERRY PIN, or the like).

Next at step 620, the server 310 may generate another reply ID andassociate the reply ID with reply message 340 in a similar fashion asdiscussed above for electronic message 330. Server 310 may also generateanother message ID, which establishes a correlation between the messagecontent of reply message 340 and header information for reply message340. Header information and message content for reply message 340 arehandled and stored similarly as described above with respect toelectronic message 330. Reply message 340 may be viewed by its recipientin the same manner as original electronic message 330 was viewed.

Advantageously, the system 300 allows the users of the computers 315 and320 to have a private conversation over network 325. After messages,such as electronic message 330 and reply message 340, are communicatedthe sender leaves no proof of the message on his or her computer. In oneexample, after the recipient views the message (or at anotherpredetermined time), the message no longer exists on system 300, thusensuring that the message cannot be forensically recreated and ensuringthat there is no record of the message remaining on system 300. Inanother example, no copies of an electronic message are ever deliveredto a user computer. In such an example, only non-caching display imagesof header information and message content are displayed separately. Theheader information and message content may be immediately,automatically, and permanently deleted from the system upon display.Once each display image is closed, the information is gone forever.Thus, in this example, there is never a copy on the user computer to bearchived, forwarded, copied, pasted, etc. In another aspect, separatedisplay of header information and message content prevents a singlescreen capture at a user computer from creating a complete record of theelectronic message. In yet another aspect, a system and method accordingto the present disclosure may provide an end-to-end recordlesselectronic messaging system that upon the deletion of the electronicmessage leaves no trace of the message content, header information, orthe fact that it was created, existed, delivered, viewed, etc.

FIG. 4 is a schematic diagram depicting a system 400 having analternative network topology. The embodiment of FIG. 4 is substantiallysimilar to that of FIG. 3, except that system 400 of FIG. 4 employs twomessage servers 405 and 410 operably coupled to user computers 415 and420 by one or more networks 425. In the embodiment of FIG. 4, the twomessage servers 415 and 420 together perform the tasks previouslydescribed for the single message server 310 of FIG. 3. For example, inthe method for sending the initial message 330, message server 405 mayperform steps 505 to 535 and a portion of step 540 of FIG. 5, whilemessage server 410 acts as the “recipient location” and performs aportion of step 540 and steps 545 to 585 of FIG. 5. It will beappreciated that both servers 405 and 410 may keep track of the reply IDand both servers 405 and 410 delete the message after it has been passedalong. This arrangement is particularly useful where message servers 405and 410 are each associated with a different enterprise, businessorganization, LAN, or the like.

It is to be noted that the above described aspects and embodiments maybe conveniently implemented using a conventional general purposecomputer programmed according to the teachings of the presentspecification, as will be apparent to those skilled in the computer art.Appropriate software coding can readily be prepared by skilledprogrammers based on the teachings of the present disclosure, as will beapparent to those skilled in the software art.

Such software can be a computer program product which employs a storagemedium including stored computer code which is used to program acomputer to perform the disclosed function and process of the presentinvention. The storage medium may include, but is not limited to, anytype of conventional floppy disks, optical disks, CD-ROMs,magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnetic or opticalcards, or any other suitable media for storing electronic instructions.

Exemplary embodiments have been disclosed above and illustrated in theaccompanying drawings. It will be understood by those skilled in the artthat various changes, omissions and additions may be made to that whichis specifically disclosed herein without departing from the spirit andscope of the present invention.

What is claimed is:
 1. A method of handling an electronic messagebetween a sending user device and a recipient user device in a networkedenvironment, the method comprising: providing a first reducedtraceability electronic messaging application program to a sending userdevice, the first reduced traceability electronic messaging applicationprogram including instructions executable by a first processor of thesending user device to provide a first plurality of reduced traceabilitydisplays via the sending user device; providing a second reducedtraceability electronic messaging application program to a recipientuser device, the second reduced traceability electronic messagingapplication program including instructions executable by a secondprocessor of the recipient user device to provide a second plurality ofreduced traceability displays via the recipient user device; receivingan electronic message at a server via a first network, the electronicmessage sent from the sending user device, wherein the electronicmessage received at the server includes an identifier of a recipient anda message content including a media component, the media componentincluding an image, the first plurality of reduced traceability displaysincluding a first display and a second display, the first displayconfigured to allow a user of the sending user mobile device toassociate the message content including a media component with theelectronic message, the second display configured to allow the user ofthe sending user mobile device to associate the identifier of arecipient with the electronic message, the instructions executable bythe first processor providing the first and second displays such thatthe identifier of the recipient is not displayed with the mediacomponent via the first display preventing a single screen capture ofboth the identifier of a recipient and the media component and theinstructions executable by the first processor provide the first andsecond displays such that the media component is not displayed with theidentifier of the recipient via the second display preventing a singlescreen capture of both the identifier of a recipient and the mediacomponent; transmitting the electronic message from the server to therecipient user device via a second network that includes a wirelesscommunications portion, wherein the electronic message transmitted tothe recipient user device includes an identifier of a sending user andthe message content including a media component, the second plurality ofreduced traceability displays including a third display and a fourthdisplay, the third display presenting the identifier of a sending user,the fourth display presenting the media component, the instructionsexecutable by the second processor providing the third and fourthdisplays such that the identifier of a sending user is not displayedwith the media component via the fourth display preventing a singlescreen capture of both the identifier of a sending user and the mediacomponent and the instructions executable by the second processorprovide the third and fourth displays such that the media component isnot displayed with the identifier of a sending user via the thirddisplay preventing a single screen capture of both the identifier of asending user and the media component; and deleting the electronicmessage from the server after the electronic message is transmitted tothe recipient user device.
 2. A method according to claim 1, wherein thefirst display and the second display are not displayed via the sendinguser device at the same time.
 3. A method according to claim 1, whereinthe third display and the fourth display are not displayed via therecipient user device at the same time.
 4. A method according to claim1, wherein the first display and the second display are not displayedvia the sending user device at the same time and wherein the thirddisplay and the fourth display are not displayed via the recipient userdevice at the same time.
 5. A method according to claim 1, wherein saidreceiving an electronic message at a server includes receiving theidentifier of a recipient and the message content including a mediacomponent separately, the server relating the identifier of a recipientand the message content including a media component using a correlationincluded in each of the identifier of a recipient and the messagecontent including a media component.
 6. A method according to claim 1,wherein said transmitting the electronic message from the server to therecipient user device includes transmitting the identifier of a sendinguser and the message content including a media component separately tothe recipient user device.
 7. A method according to claim 1, whereinsaid deleting the electronic message includes deleting the electronicmessage from the server after the fourth display is provided.
 8. Amethod according to claim 1 wherein said deleting the electronic messageincludes deleting the electronic message from the server after thefourth display is provided and upon the fourth display no longer beingprovided.
 9. A computer readable hardware storage medium containingmachine executable instructions implementing a method of handling anelectronic message between a sending user device and a recipient userdevice in a networked environment, the electronic message includingheader information and a message content, the instructions comprising: aset of instructions executable by a first processor of the sending userdevice to provide a first plurality of reduced traceability displays viathe sending user device; a set of instructions executable by a secondprocessor of the recipient user device to provide a second plurality ofreduced traceability displays via the recipient user device; a set ofinstructions for receiving an electronic message at a server via a firstnetwork, the electronic message sent from the sending user device, theelectronic message received at the server including an identifier of arecipient and a message content including a media component, the mediacomponent including an image, the first plurality of reducedtraceability displays including a first display and a second display,the first display configured to allow a user of the sending user mobiledevice to associate the message content including a media component withthe electronic message, the second display configured to allow the userof the sending user mobile device to associate the identifier of arecipient with the electronic message, the instructions executable bythe first processor providing the first and second displays such thatthe identifier of the recipient is not displayed with the mediacomponent via the first display preventing a single screen capture ofboth the identifier of a recipient and the media component and theinstructions executable by the first processor provide the first andsecond displays such that the media component is not displayed with theidentifier of the recipient via the second display preventing a singlescreen capture of both the identifier of a recipient and the mediacomponent; and a set of instructions for transmitting the electronicmessage from the server to the recipient user device via a secondnetwork that includes a wireless communications portion, the electronicmessage including an identifier of a sending user and the messagecontent including a media component, the second plurality of reducedtraceability displays including a third display and a fourth display,the third display presenting the identifier of a sending user, thefourth display presenting the media component, the instructionsexecutable by the second processor providing the third and fourthdisplays such that the identifier of a sending user is not displayedwith the media component via the fourth display preventing a singlescreen capture of both the identifier of a sending user and the mediacomponent and the instructions executable by the second processorprovide the third and fourth displays such that the media component isnot displayed with the identifier of a sending user via the thirddisplay preventing a single screen capture of both the identifier of asending user and the media component; and a set of instructions fordeleting the electronic message from the server after the electronicmessage is transmitted to the recipient user device.
 10. A computerreadable hardware storage medium according to claim 9, wherein the firstdisplay and the second display are not displayed via the sending userdevice at the same time.
 11. A computer readable hardware storage mediumaccording to claim 9, wherein the third display and the fourth displayare not displayed via the recipient user device at the same time.
 12. Acomputer readable hardware storage medium according to claim 9, whereinthe first display and the second display are not displayed via thesending user device at the same time and wherein the third display andthe fourth display are not displayed via the recipient user device atthe same time.
 13. A computer readable hardware storage medium accordingto claim 9, wherein said set of instructions for receiving an electronicmessage at a server includes a set of instructions for receiving theidentifier of a recipient and the message content including a mediacomponent separately, the server relating the identifier of a recipientand the message content including a media component using a correlationincluded in each of the identifier of a recipient and the messagecontent including a media component.
 14. A computer readable hardwarestorage medium according to claim 9, wherein said set of instructionsfor transmitting the electronic message from the server to the recipientuser device includes a set of instructions for transmitting theidentifier of a sending user and the message content including a mediacomponent separately to the recipient user device.
 15. A computerreadable hardware storage medium according to claim 9, wherein said setof instructions for deleting the electronic message includes a set ofinstructions for deleting the electronic message from the server afterthe fourth display is provided.
 16. A computer readable hardware storagemedium according to claim 9, wherein said set of instructions fordeleting the electronic message includes a set of instructions fordeleting the electronic message from the server after the fourth displayis provided and upon the fourth display no longer being provided.